home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.19980901-19981211 / 000192_news@newsmaster….columbia.edu _Fri Oct 23 06:09:22 1998.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB
  1. Return-Path: <news@newsmaster.cc.columbia.edu>
  2. Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
  3.     by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id GAA02674
  4.     for <kermit.misc@watsun.cc.columbia.edu>; Fri, 23 Oct 1998 06:09:21 -0400 (EDT)
  5. Received: (from news@localhost)
  6.     by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id GAA10030
  7.     for kermit.misc@watsun; Fri, 23 Oct 1998 06:09:20 -0400 (EDT)
  8. Path: news.columbia.edu!panix!howland.erols.net!netnews.com!news.maxwell.syr.edu!news.mel.connect.com.au!psdcomms.pronto.com.au!stuart
  9. From: stuart@psd.com.au (Stuart Park)
  10. Newsgroups: comp.protocols.kermit.misc,comp.os.linux.misc
  11. Subject: Re: CKermit 6.1beta rpm?
  12. Followup-To: comp.protocols.kermit.misc,comp.os.linux.misc
  13. Date: 23 Oct 1998 07:44:30 GMT
  14. Organization: Prometheus Software
  15. Lines: 24
  16. Message-ID: <70pc4u$piu@psdcomms.pronto.com.au>
  17. References: <7093jk$hpl$1@eskinews.eskimo.com> <709arq$ajk$1@samba.rahul.net> <70dgmp$1i9$1@post.servtech.com> <70ju4k$567$1@eskinews.eskimo.com> <70kpvd$7mu$1@apakabar.cc.columbia.edu>
  18. NNTP-Posting-Host: ibmj30
  19. X-Newsreader: TIN [version 1.2 PL2]
  20. Xref: news.columbia.edu comp.protocols.kermit.misc:9388 comp.os.linux.misc:303787
  21.  
  22. Frank da Cruz (fdc@watsun.cc.columbia.edu) wrote:
  23. <snip..>
  24. : To some extent -- some people have trouble, some don't.  I can't
  25. : necessarily keep up with all the variations in the many Linux
  26. : distributions and versions of them.  What was the Right Way to do a
  27. : particular one day often becomes Horribly Wrong the next.
  28. <snip..>
  29.  
  30. It's probably best to just stick with one version of Linux (e.g. Redhat)
  31. and emphasize that in any documentation, and then it is up to package
  32. maintainers etc to configure the relevant parts.  Actually the Redhat
  33. people seem to be pretty good at making small modifications to software
  34. to suit their releases, and you could then have available the "rpm" they
  35. create.  The same could apply to other versions e.g. Debian.
  36.  
  37. It really shouldn't have to be the responsibility of a generic product
  38. such as kermit to handle every single combination of Linux kernel and
  39. libraries.. leave that responsibility to the package maintainers.
  40.  
  41.  
  42. --
  43. Stuart Park                             Melbourne, Australia
  44. Senior Analyst                          E-mail: stuart@pronto.com.au
  45. Prometheus Software